Hi, i know it's possible to move addins e project path, but i would like to know if it would be possible to change the default path for the folder "dxl". Thanks bungle_77 - Mon Sep 26 05:30:18 EDT 2016 |
Re: changing "lib/dxl" path Inside the DXL folder there are lots of files, that the DOORS interpreter needs. So redefining the location of this folder is probably not possible. Why would you want to do that? You could probably achieve the same result, by simply removing unwanted files from there or adding files in an "ADDINS" location for them to be available inside the client(s). Regards, Mathias |
Re: changing "lib/dxl" path You can always change the location by changing the location where you install DOORS. |
Re: changing "lib/dxl" path I realized a framework that i use in several environments, in one of this environement i want to centralize it on a shared path. The main problem is that my dxl files have a lot of inclusions, so the include instruction should change according to the environment i should install the framework. For example: Environment #1: #include <librariesPath/LibFile.inc>
Environment #2: #include "%CENTALIZED_PATH%/librariesPath/LibFile.inc"
So in this way, everytime i have to release my framework for environment #2 i should change all the include instructions. Of course i could define a global variable and make parametric inclusions, but anyway i have to include the file with global variable. Ohter solution is to centralize only the dxl script in addins and project folder and copy locally all the libraries.
So now my further questions are:
I hope it does make sense what i said |
Re: changing "lib/dxl" path bungle_77 - Tue Sep 27 04:20:42 EDT 2016 I realized a framework that i use in several environments, in one of this environement i want to centralize it on a shared path. The main problem is that my dxl files have a lot of inclusions, so the include instruction should change according to the environment i should install the framework. For example: Environment #1: #include <librariesPath/LibFile.inc>
Environment #2: #include "%CENTALIZED_PATH%/librariesPath/LibFile.inc"
So in this way, everytime i have to release my framework for environment #2 i should change all the include instructions. Of course i could define a global variable and make parametric inclusions, but anyway i have to include the file with global variable. Ohter solution is to centralize only the dxl script in addins and project folder and copy locally all the libraries.
So now my further questions are:
I hope it does make sense what i said that's no problem. IIRC, DOORS will look for include files in - currentDirectory() (that's the working directory defined in the link to start DOORS, which might be changed programatically) - %DOORSHOME%/lib/dxl - %DOORSADDINS% - %ADDINS% - %DOORSPROJECTADDINS% - %PROJECTADDINS% - and/or the directories defined in the DOORS link at -projectaddins and -addins |
Re: changing "lib/dxl" path bungle_77 - Tue Sep 27 04:20:42 EDT 2016 I realized a framework that i use in several environments, in one of this environement i want to centralize it on a shared path. The main problem is that my dxl files have a lot of inclusions, so the include instruction should change according to the environment i should install the framework. For example: Environment #1: #include <librariesPath/LibFile.inc>
Environment #2: #include "%CENTALIZED_PATH%/librariesPath/LibFile.inc"
So in this way, everytime i have to release my framework for environment #2 i should change all the include instructions. Of course i could define a global variable and make parametric inclusions, but anyway i have to include the file with global variable. Ohter solution is to centralize only the dxl script in addins and project folder and copy locally all the libraries.
So now my further questions are:
I hope it does make sense what i said 1. yes, when you have a relative include statement DOORS will look at different places, e.g. the current directory, PROJECT_ADDINS, LAYOUT_ADDINS, ADDINS, etc. 2. no, since includes are executed during translation of the DXL code (the file contents are simply dumped into the location). You can use an eval_ statement though to trigger conditional includes at runtime. So you can put the code of your one framework on a common share and add it to (any) include path. Maybe this helps, regards, Mathias |
Re: changing "lib/dxl" path Ok thanks, i solved defined an environmental variable and using getenv |
Re: changing "lib/dxl" path Mathias Mamsch - Tue Sep 27 05:16:05 EDT 2016 1. yes, when you have a relative include statement DOORS will look at different places, e.g. the current directory, PROJECT_ADDINS, LAYOUT_ADDINS, ADDINS, etc. 2. no, since includes are executed during translation of the DXL code (the file contents are simply dumped into the location). You can use an eval_ statement though to trigger conditional includes at runtime. So you can put the code of your one framework on a common share and add it to (any) include path. Maybe this helps, regards, Mathias Hi Matthias,
I copied the "DXL Libraries" folder containing the"ProjectConfigurationParameters.inc" file in the path "%DOORSHOME%\lib\dxl\addins" #include </DXL Libraries/ProjectConfigurationParameters.inc> but it give me an error
I tried to define also %DOORSADDINS% environment variable. but nothing
If i change the default addins path and i launch doors with -J %Project% -a %Addins% it works.
But do you know why with default addins path is not working? |
Re: changing "lib/dxl" path bungle_77 - Tue Sep 27 06:27:12 EDT 2016 Hi Matthias,
I copied the "DXL Libraries" folder containing the"ProjectConfigurationParameters.inc" file in the path "%DOORSHOME%\lib\dxl\addins" #include </DXL Libraries/ProjectConfigurationParameters.inc> but it give me an error
I tried to define also %DOORSADDINS% environment variable. but nothing
If i change the default addins path and i launch doors with -J %Project% -a %Addins% it works.
But do you know why with default addins path is not working? #include </DXL Libraries/ProjectConfigurationParameters.inc> should be #include <DXL Libraries/ProjectConfigurationParameters.inc>
|
Re: changing "lib/dxl" path Mike.Scharnow - Tue Sep 27 06:29:47 EDT 2016 #include </DXL Libraries/ProjectConfigurationParameters.inc> should be #include <DXL Libraries/ProjectConfigurationParameters.inc>
the first "/" is redundant... andyway it's not working also without |
Re: changing "lib/dxl" path bungle_77 - Tue Sep 27 06:37:04 EDT 2016 the first "/" is redundant... andyway it's not working also without Searching include path problems is always a hassle... You should fireup procmon from sysinternals to really see which paths the DOORS client is searching, when you make include "abcdef.dxl" ... This usually immediately makes the problems obvious. My guess is, that normally the addins include path is ob "lib/dxl" not on addins. Therefore you need to probably include
#include <addins/DXL Libraries/...>
Regards, Mathias |
Re: changing "lib/dxl" path Mathias Mamsch - Tue Sep 27 06:45:09 EDT 2016 Searching include path problems is always a hassle... You should fireup procmon from sysinternals to really see which paths the DOORS client is searching, when you make include "abcdef.dxl" ... This usually immediately makes the problems obvious. My guess is, that normally the addins include path is ob "lib/dxl" not on addins. Therefore you need to probably include
#include <addins/DXL Libraries/...>
Regards, Mathias if i use #include <addins/DXL Libraries/...> i come back to my original problem
i tried to download procmon but i can find the path, i am not so good to use it.
Anyway i solved the problem using -J %Project% -a %Addins% .
Thanks a lot |